kermit.columbia.edu/kermit.columbia.edu.tar/kermit.columbia.edu/newsgroups/misc.19960425-19960715/[e-mail] _Wed Jul 3 19:27:43 1996.msg

Internet Message Format | 1996-07-26 | 2KB

Return-Path: [e-mail]
Received: from apakabar.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30]) by watsun.cc.columbia.edu (8.7.5/8.7.3) with ESMTP id TAA00447 for <[e-mail]>; Wed, 3 Jul 1996 19:27:42 -0400 (EDT)
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.7.5/8.7.3) id TAA29423 for kermit.misc@watsun; Wed, 3 Jul 1996 19:27:42 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: [e-mail] (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: whose side comm params take precedence?
Date: 3 Jul 1996 23:27:37 GMT
Organization: Columbia University
Lines: 19
Message-ID: <4revl9$[e-mail]>
References: <[e-mail]>
NNTP-Posting-Host: watsun.cc.columbia.edu

In article <[e-mail]>,
Vladimir Alexiev  <[e-mail]> wrote:
: If two kermits have different communication parameters set, which ones take
: precedence? I think for send/receive the packet size of the receiver takes
: precedence, or is the minimum of the two used?
:
The answer depends on the parameter.  See Table 8-1 on page 168 of "Using
C-Kermit".

The maximum packet length is governed by the receiver.  That is, by whatever
SET RECEIVE PACKET-LENGTH you give to the file receiver.  You can give a
SET SEND PACKET-LENGTH command to the sender, but you can only use it to
make the packets smaller, not larger.

The sender can, of course, unilaterally decide to send a packet of any
length at all, up to the maximum negotiated length.  And that's what happens
when errors occur.

- Frank